[Support Feedback] Improve IUAM, DDoS triage, and origin protection docs (DDoS Protection)#28994
Open
dmmulroy wants to merge 4 commits intocloudflare:productionfrom
Open
[Support Feedback] Improve IUAM, DDoS triage, and origin protection docs (DDoS Protection)#28994dmmulroy wants to merge 4 commits intocloudflare:productionfrom
dmmulroy wants to merge 4 commits intocloudflare:productionfrom
Conversation
dmmulroy
requested review from
a team,
dcpena and
patriciasantaana
as code owners
…cs from support macro audit SPM-3037
dmmulroy
force-pushed
the
support-macros/ddos-protection
branch
from
c833b49 to
57368c3
Compare
…Attack mode explanation
zeinjaber
reviewed
Mar 17, 2026
|
|
||
| ### Selectively disable for specific areas | ||
|
|
||
| If you have enabled Under Attack mode site-wide but it breaks certain parts of your site (for example, API endpoints or areas that serve non-browser traffic), use a [configuration rule](/rules/configuration-rules/) to set the security level to a lower value for those paths. |
Contributor
There was a problem hiding this comment.
This statement ...to set the security level to a lower value for those paths. is incorrect.
Customers can no longer able to change levels (low, medium, etc..).
I'd suggest changing it to ...to disable I’m Under Attack for those paths.
| - **Under Attack mode applies challenges at Cloudflare's edge.** Challenge outcomes are recorded in [Cloudflare security analytics](/waf/analytics/security-events/). Requests reach your origin only after a challenge is solved, via a valid `cf_clearance` cookie, or when traffic is excluded from Under Attack mode through configuration rules. | ||
| - **Non-browser traffic will be blocked.** Under Attack mode requires JavaScript execution, so API clients, mobile apps, and automated integrations will fail the challenge. Use configuration rules or WAF custom rules to exclude these paths or traffic types. | ||
| - **Disable when the attack subsides.** Under Attack mode is designed as a temporary measure. Once attack traffic returns to normal, turn it off to avoid unnecessarily challenging legitimate visitors. | ||
| - **Consider customizing the challenge page.** You can brand the interstitial page shown to visitors during the challenge. Go to **Configurations** > **Custom Pages** > **Managed Challenge / I'm Under Attack Mode** to configure a custom page. |
Contributor
There was a problem hiding this comment.
Let's change: Go to **Configurations** > **Custom Pages**
To: Go to **Configurations** > **Error Pages**
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Expands DDoS protection documentation for common support topics, based on an audit of active support macros.
Changes
Context
These changes are driven by recurring support cases. If you want to see the underlying support data (macro frequency, case volume by topic), reach out to @dmmulroy internally.